fix!: Code refactoring to patch broken local dev setup #646
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This addresses issues related to the local environment setup by skipping any
Bearer
token assignment or connection to GCP. Running the project withSM_ENVIRONMENT=LOCAL
was raising auth-related GCPClient errors as the project looked for GCP credentials. Technically, this shouldn't be necessary when running locally.Changes Made
Refactored graphql/init.py for Local Environment Handling:
Modified
metamist/graphql/__init__.py
file:When running locally, the AIOHTTPTransport instance is created without the
Authorization
header.This modification prevents unnecessary authentication-related errors that were occurring during local execution.
Modified the
openapi-templates/configuration.mustache
template:Updated the OpenAPI configuration.mustache template to accommodate local environment nuances.
Specifically, the
auth_settings
class method now returns an empty auth object when the application is running locally.